-
Notifications
You must be signed in to change notification settings - Fork 2
feat(config): accept multiple entrypoints for build #149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SCC Complexity Analysis
|
jotanarciso
pushed a commit
that referenced
this pull request
Apr 4, 2025
[skip ci] ## [1.18.0-stage.3](v1.18.0-stage.2...v1.18.0-stage.3) (2025-04-04) ### Features * **config:** accept multiple entrypoints for build (#149) ([556173e](556173e))
🎉 This PR is included in version 1.18.0-stage.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
jotanarciso
added a commit
that referenced
this pull request
Apr 10, 2025
* feat(config): accept multiple entrypoints for build (#148) * feat(bundler): support multiple entrypoints * feat(schema): accept multiple entries * fix: add outDir BuildContext * chore: BuildContext outDir optional * chore: rm cli postinstall * chore: rm debug * refactor(config): buildContext * fix(presets): next.js postbuild * refactor(bundler): rm .dev sufix * chore: fix test file * test: update tests * fix(esbuild): define default outdir * test: resolve jest * chore: fix tests and add jest globals for testing * docs: update config docs --------- Co-authored-by: José Filho <jc.bsfilho@gmail.com> * ci: rm azion cli bin step * chore(release): 1.18.0-stage.1 [skip ci] ## [1.18.0-stage.1](v1.17.4...v1.18.0-stage.1) (2025-04-04) ### Features * **config:** accept multiple entrypoints for build (#148) ([9f58e50](9f58e50)) * Revert "chore(release): 1.18.0-stage.1" This reverts commit 6b6f003. * Revert "feat(config): accept multiple entrypoints for build (#148)" This reverts commit 9f58e50. * chore(release): 1.18.0-stage.2 [skip ci] ## [1.18.0-stage.2](v1.18.0-stage.1...v1.18.0-stage.2) (2025-04-04) ### Reverts * Revert "feat(config): accept multiple entrypoints for build (#148)" ([daad9db](daad9db)) * Revert "chore(release): 1.18.0-stage.1" ([f458098](f458098)) * feat(config): accept multiple entrypoints for build (#149) * feat(bundler): support multiple entrypoints * feat(schema): accept multiple entries * fix: add outDir BuildContext * chore: BuildContext outDir optional * chore: rm cli postinstall * chore: rm debug * refactor(config): buildContext * fix(presets): next.js postbuild * refactor(bundler): rm .dev sufix * chore: fix test file * test: update tests * fix(esbuild): define default outdir * test: resolve jest * chore: fix tests and add jest globals for testing * docs: update config docs --------- Co-authored-by: José Filho <jc.bsfilho@gmail.com> * chore(release): 1.18.0-stage.3 [skip ci] ## [1.18.0-stage.3](v1.18.0-stage.2...v1.18.0-stage.3) (2025-04-04) ### Features * **config:** accept multiple entrypoints for build (#149) ([556173e](556173e)) --------- Co-authored-by: José Filho <jc.bsfilho@gmail.com> Co-authored-by: semantic-release-bot <semantic-release-bot@martynus.net>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.